Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-66419 | JUSX-IP-000017 | SV-80909r1_rule | Medium |
Description |
---|
If the network does not provide safeguards against DoS attack, network resources will be unavailable to users. Installation of IDPS detection and prevention components (i.e., sensors) at key boundaries in the architecture mitigates the risk of DoS attacks. These attacks can be detected by matching observed communications traffic with patterns of known attacks and monitoring for anomalies in traffic volume/type. Detection components that use rate-based behavior analysis can detect attacks when signatures for the attack do not exist or are not installed. These attacks include zero-day attacks which are new attacks for which vendors have not yet developed signatures. Rate-based behavior analysis can detect sophisticated, Distributed DoS (DDoS) attacks by correlating traffic information from multiple network segments or components. The Juniper SRX must be configured with screens using the Firewall STIG, but must also be configured for anomaly-based protection using various locally developed anomaly-based attack objects. |
STIG | Date |
---|---|
Juniper SRX SG IDPS Security Technical Implementation Guide | 2017-07-07 |
Check Text ( C-67065r1_chk ) |
---|
From operational mode, enter the following command to verify that the anomaly-based attack object was created: show idp security policies If anomaly-based attack objects are not created, bound to a zone, and active, this is a finding. |
Fix Text (F-72495r1_fix) |
---|
Create a protocol anomaly-based attack object: Specify a name for the attack. [edit] security idp custom-attack anomaly1 Specify common properties for the attack. [edit security idp custom-attack anomaly1] set severity info set time-binding scope peer count 2 Specify the attack type and test condition. [edit] security idp custom-attack anomaly1set attack-type anomaly test OPTIONS_UNSUPPORTED Specify other properties for the anomaly attack. [edit] security idp custom-attack anomaly1] set attack-type anomaly service TCP u set attack-type anomaly direction any attack-type anomaly shellcode spark |